|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 4614 (2006)
|
|
Title:
|
A Roadmap for Transmission Control Protocol (TCP) Specification Documents
|
|
|
2.
|
Status of approval:
|
|
|
Informal RFC approved September 2006.
|
|
3.
|
Justification for the specific reference:
|
|
|
ITU-T H.810 requires the use of this informational RFC, A Roadmap for Transmission Control Protocol (TCP) Specification Documents, as a library of documents required for implementing TCP for use over the Continua WAN Interface defined in H.810. It serves as a quick reference for both TCP implementers and other parties who desire information contained in the TCP-related RFCs. The correct and efficient implementation of the Transmission Control Protocol (TCP) for certification of H.810 devices is a critical part of the software of most Internet hosts. As TCP has evolved over the years, many distinct documents have become part of the accepted standard for TCP. At the same time, a large number of more experimental modifications to TCP have also been published in the RFC series, along with informational notes, case studies, and other advice. This document is used as a brief summary of the RFC documents that define TCP and provides guidance to implementers on the relevance and signifcance of RFC extensions, informational notes, and best current practices tat relate to TCP.This specification has been very helpful in both helping Continua create its source code and its automated test program. The same guidance has been utilized by implementers who have certified WAN devices at Continua Health Alliance.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
N/A.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Informational RFC approved September 2006. Updated by RFC 6247.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Specification approved September 2006.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Specification approved September 2006.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[RFC0793] Postel, J., "Transmission Control Protocol", STD 7, RFC 793, September 1981./
/
[RFC1122] Braden, R., "Requirements for Internet Hosts - Communication Layers", STD 3, RFC 1122, October 1989./
/
[RFC2026] Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996./
/
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998./
/
[RFC2474] Nichols, K., Blake, S., Baker, F., and D. Black, "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers", RFC 2474, December 1998./
/
[RFC2581] Allman, M., Paxson, V., and W. Stevens, "TCP Congestion Control", RFC 2581, April 1999./
/
[RFC2675] Borman, D., Deering, S., and R. Hinden, "IPv6 Jumbograms", RFC 2675, August 1999./
/
[RFC2873] Xiao, X., Hannan, A., Paxson, V., and E. Crabbe, "TCP Processing of the IPv4 Precedence Field", RFC 2873, June 2000./
/
[RFC2988] Paxson, V. and M. Allman, "Computing TCP's Retransmission Timer", RFC 2988, November 2000. 10.2. Recommended Enhancements/
/
[RFC1323] Jacobson, V., Braden, R., and D. Borman, "TCP Extensions for High Performance", RFC 1323, May 1992./
/
[RFC1948] Bellovin, S., "Defending Against Sequence Number Attacks", RFC 1948, May 1996./
/
[RFC2018] Mathis, M., Mahdavi, J., Floyd, S., and A. Romanow, "TCP Selective Acknowledgment Options", RFC 2018, October 1996./
/
[RFC2385] Heffernan, A., "Protection of BGP Sessions via the TCP MD5 Signature Option", RFC 2385, August 1998.
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
N/A.
|
|
